Add support for Jelbert GeoTagger data files (.jtr).

diff --git a/vecs.c b/vecs.c
index abfb2f3c83f53c5bbbff4d063e3ca0e433700f81..a6f48b0f1d2b1a8e8bfae72c236d16bc39333d03 100644 (file)
--- a/vecs.c
+++ b/vecs.c
@@ -850,7 +850,7 @@ vecs_t vec_list[] = {
 #if CSVFMTS_ENABLED
         {
                 &geotagger_vecs,
-                "geotagger",
+                "jtr",
                 "Jelbert GeoTagger data file",
                 "jtr"
         },

diff --git a/xmldoc/formats/jtr.xml b/xmldoc/formats/jtr.xml
new file mode 100644 (file)
index 0000000..0d39be4
--- /dev/null
+++ b/xmldoc/formats/jtr.xml
@@ -0,0 +1,28 @@
+<para>
+   From the <ulink url="http://www.geotagger.co.uk/files/JTR_Format.pdf">file format description</ulink>:
+</para>
+<para>
+   The JTR file format is used by the Jelbert GeoTagger device to record
+   location information relating to where photographs have been taken.
+   One record entry is created for each press of the shutter on the
+   camera.
+</para>
+<para>
+   The JTR file format will be updated in the future so it is important to
+   check for the current version ID within the file that is present at the
+   beginning of each line of data. It is currently “GEOTAG2”
+</para>
+<para>
+   Each line of the JTR file currently starts with the word “GEOTAG2”
+   followed by a comma and then two NMEA sentences separated by a
+   comma character with a CR at the end. The $GPRMC (date, time and
+   position) data is followed by the $HCHDG (magnetic compass) data.
+</para>
+<para>
+   Although the $GPRMC data segment contains a compass bearing, this
+   should be ignored unless the $HCHDG compass direction is null which
+   can happen if the electronic compass is switched off. Use the magnetic
+   compass bearing in preference to the GPS derived compass.
+   The two NMEA checksums can be ignored for the time being.
+</para>
+